-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore_permission_denied #80
Conversation
41f65bf
to
3eb321c
Compare
Unfortunately, simply passing
You can find a full description of the problem we are facing in the With this
|
3eb321c
to
ed9ac16
Compare
ed9ac16
to
0a57fc7
Compare
You wrote on the watchfiles issue:
Let’s wait and see what Samuel replies. |
@adamchainz , Hey Adam! There's been no reply in my PR to watchfiles for a month. Do you think you could now consider merging this PR into django-watchfiles? If my PR is merged into |
Samuel has been busy launching Pydantic Logfire: https://pydantic.dev/ . I would still wait for a reply there. Until then you can install your fork, if you're not already: https://adamj.eu/tech/2019/03/11/pip-install-from-a-git-repository/ I would rather not merge any workarounds here. django-watchfiles is still alpha and I'd rather only add things we're sure we need, to iterate towards a 1.0.0 release. |
If I understand correctly from these comments: notify-rs/notify#581 (comment) Then your issue has been fixed with watchfiles 0.24.0. I am going to close this for now, then. Adding Thank you for providing enough links to chase up on! |
There is no reason to stop Django process and exit with error when watch encounters an incident such as an unreadable file, "permission denied" etc. So it seems reasonable to me to always pass
ignore_permission_denied=True
towatchfiles
.See also samuelcolvin/watchfiles#224, where this flag was introduced.